Unauthorized kernel modules must not be loaded on the host.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
SRG-OS-99999-ESXI5-000158	SRG-OS-99999-ESXI5-000158	SRG-OS-99999-ESXI5-000158_rule		Medium

Description
VMware provides digital signatures for kernel modules. By default, the ESXi host does not permit loading of kernel modules that lack a valid digital signature. However, this behavior can be overridden, allowing unauthorized kernel modules to be loaded. Untested or malicious kernel modules loaded on the ESXi host can put the host at risk for instability and/or exploitation.

STIG	Date
VMware ESXi v5 Security Technical Implementation Guide	2013-01-15

Details

Check Text ( C-SRG-OS-99999-ESXI5-000158_chk )
Temporarily disable Lockdown Mode and enable the ESXi Shell via the vSphere Client. Open the vSphere/VMware Infrastructure (VI) Client and log in with appropriate credentials. If connecting to vCenter Server, click on the desired host. Click the Configuration tab. Click Software, Security Profile, Services, Properties, ESXi Shell and Options, respectively. Start the ESXi Shell service, where/as required. As root, log in to the host and perform the following: Inspect the host for unsigned kernel modules. To list all the loaded kernel modules run: # esxcli system module list For each host module verify the signature by running: # esxcli system module get -m " If the host's module list contains any unsigned modules, this is a finding. Re-enable Lockdown Mode on the host.

Check Text ( C-SRG-OS-99999-ESXI5-000158_chk )

Temporarily disable Lockdown Mode and enable the ESXi Shell via the vSphere Client.

Open the vSphere/VMware Infrastructure (VI) Client and log in with appropriate credentials.
If connecting to vCenter Server, click on the desired host.
Click the Configuration tab.
Click Software, Security Profile, Services, Properties, ESXi Shell and Options, respectively.
Start the ESXi Shell service, where/as required.

As root, log in to the host and perform the following:
Inspect the host for unsigned kernel modules. To list all the loaded kernel modules run:
# esxcli system module list

For each host module verify the signature by running:
# esxcli system module get -m "

If the host's module list contains any unsigned modules, this is a finding.

Re-enable Lockdown Mode on the host.

Fix Text (F-SRG-OS-99999-ESXI5-000158_fix)
Temporarily disable Lockdown Mode and enable the ESXi Shell via the vSphere Client. Open the vSphere/VMware Infrastructure (VI) Client and log in with appropriate credentials. If connecting to vCenter Server, click on the desired host. Click the Configuration tab. Click Software, Security Profile, Services, Properties, ESXi Shell and Options, respectively. Start the ESXi Shell service, where/as required. As root, log in to the host and perform the following: Secure the host by individually disabling unsigned modules and removing the offending VIBs from the host. Note that in order to disable kernel modules, from the vSphere Client, VMs must first be evacuated and the host must then be placed into maintenance mode. # esxcli system modules set -e false -m Re-enable Lockdown Mode on the host.

Fix Text (F-SRG-OS-99999-ESXI5-000158_fix)

Temporarily disable Lockdown Mode and enable the ESXi Shell via the vSphere Client.

Open the vSphere/VMware Infrastructure (VI) Client and log in with appropriate credentials.
If connecting to vCenter Server, click on the desired host.
Click the Configuration tab.
Click Software, Security Profile, Services, Properties, ESXi Shell and Options, respectively.
Start the ESXi Shell service, where/as required.

As root, log in to the host and perform the following:

Secure the host by individually disabling unsigned modules and removing the offending VIBs from the host.
Note that in order to disable kernel modules, from the vSphere Client, VMs must first be evacuated and the host must then be placed into maintenance mode.
# esxcli system modules set -e false -m

Re-enable Lockdown Mode on the host.